Looks good to me, I think the enums with _ are fine.

I think the JSONSchema for Role should include UNRECOGNIZED as an enum option, rather than trying to use a default, and the client should handle that accordingly. This is for future compatibility so that a new action does not break existing clients.

Needs changes from master merged in, for the const: schemaName change.

Ok, I see that, for example, the Field schema doesn't have an UNRECOGNIZED option on the type field (only text|number|selectOne|selectMultiple) in what sense that case is different? mostly because we're certain we are not going to add additional options in the future??

Ok, I see that, for example, the Field schema doesn't have an UNRECOGNIZED option on the type field (only text|number|selectOne|selectMultiple) in what sense that case is different? mostly because we're certain we are not going to add additional options in the future??

Ah good point. I initially had initially thought that a text field is a good fallback for anything, but because the actual values stored in the tags could be different, I think it's better for the client to decide how to deal with this, by which I mean that UNRECOGNIZED is a good option here - if the client sees that, it can look at any existing value and choose the best way to display it.

It's a different case with the appearance option, where multiline is a good fallback for any future options.